We need to remove the copy of this file from the documentation repo, and refer to this include instead, in a separate PR.

Can we do that, from another repo?

Example. Adjust relative paths as needed.

In Volto docs.

```{include} ../_inc/_install-operating-system.md
```

In documentation.

```{include} ../../volto/_inc/_install-operating-system.md
```

IOW, when you use the include in Volto, then you can refer to it in documentation, after it gets merged in a PR, of course. You cannot go the reverse direction.

Done. Removed the local inc.

That's not what I meant. Please read my original statement. The separate PR would be in Documentation.

but the original is in docs already.

We need to remove the copy of this file from the documentation repo

The docs in Volto have no idea that plone/documentation exists with regard to includes. Please restore the file /_inc/_install-operating-system.md here, restore the include directive, and we will delete the original from plone/documentation.

You can verify this by trying to build docs locally.

I wonder if we should say something more for 17.x.x? For example, let's say I have a project with Plone 6.0 and Volto 17. What should I do? Should I upgrade both Plone to 6.1 and Volto to 18? If so, then we need to also link directly to each upgrade guide.

It's not mandatory to upgrade. It can get some updates, if people still care for it, and the Volto Team approve them.

@sneridagh Steve's right, if we're saying it's no longer supported, we need to give some advice on how to move forward.

It's possible to upgrade to Volto 18 (i.e. by generating a new cookieplone project and moving your custom code over) without updating the backend to Plone 6.1.

As a side note, after seeing all the added admonitions in theming docs regarding Semantic UI, where would I look now for theming docs for the new way of theming? We should include that in the admonition, too.

Nowhere to look yet. We should start sending the message: "Whatever you use for theming your site, but SemanticUI, is fine. You can continue using it if you want, but core will abandon it in Plone 7."

I completed the info on 17.x.x

That's not what I meant. Please read my original statement. The separate PR would be in Documentation.

Let's rename it to _semantic-ui-deprecation.md because there is a space in its official brand name.

Done.

This seems to contradict line 41.

I'm adding a "legacy" entry at the top of the document to clarify it.

We should link to https://6.docs.plone.org/install/create-project-cookieplone.html here, not the Cookieplone repository.

The whole sentence needs a rewrite. This syntax should work via Intersphinx for both here and plone/documentation.

=>

For new projects, follow Install Plone with Cookieplone instead.

The next line makes it sound like it's still supported for Volto 18, we need to change that.

Does it work in 18? I assumed that if something works, then that means it's supported.

Also if something works, it can also be deprecated.

No, we started to update it for Volto 18 but then realized we needed to create Cookieplone instead, because the structure was too different.

Since it doesn't work in 18, then why do we even have it in 18? https://github.com/plone/volto/tree/main/packages/generator-volto

"It does work" but it's true that maybe we should not advertise it, it could be confusing.

Well, I just tried it, and it didn't work for me. But it could be that the Training I followed has incorrect information.

@stevepiercy there's still an acceptance test for it in place. So it should still work for 18. For project, the add-on template is not being tested. What did you do? That training could be outdated.

I followed the exact instructions published in that training, pretending to be a learner.